Node-RED block in Snap4City Microservice library node-red-contrib-snap4city-developer is "service-search-by-queryid">
    <p>It allows to retrieve the set of services associated with a query stored using the servicemap user interface. </p>

    <h3>Inputs</h3>
    A JSON with these parameters:

    <dl class="message-properties">
        <dt>queryId
            <span class="property-type">string</span>
        </dt>
        <dd> identifier of the query stored on servicemap (<a target="_blank" href="https://www.snap4city.org/drupal/node/737">info about QueryId</a>)</dd>
        <dt>lang
            <span class="property-type">string</span>
        </dt>
        <dd> ISO 2 chars language code (e.g. “it”, “en”, “fr”, “de”, “es”) to be used for returned descriptions if available in
            multiple languages. Currently for languages other than “it” and “en” it returns “en” descriptions. (if parameter
            is missing “en” is assumed)</dd>
    </dl>

    <h3>Outputs</h3>
    <ol class="node-ports">
        <li>ServiceUri Array
            <dl class="message-properties">
                <dd> Returns an array containing the servicesUri of each service found</dd>
            </dl>
        </li>
        <li>GeoJSON Results
            <dl class="message-properties">
                <dd> It returns the services split in three sections (BusStops , SensorSites, Services). Each section is provided
                    as GeoJSON “FeatureCollection”, the results are sorted by distance, additionally in each section the
                    “fullCount” property reports the full number of results available matching the query</dd>
            </dl>
        </li>
        <li> All services together
            <dl class="message-properties">
                <dd> It returns the services merge in Results section</dd>
            </dl>
        </li>
    </ol>

    <h3>Details</h3>
    <p>The node can receive a JSON with the parameters described in the Inputs section and with them generate the output JSON.
        If the values are not present in the input JSON, these are read by those in the configuration. If they are not present
        in either part, an error is generated for the necessary parameters.</p>